This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
It sounds strange that you had to do Domino.document1. You should just need to use the name you gave the datasource when referencing it is server-side javascript - this should be visible in the list of Global Objects when you're in the Script Editor.
You should be able to call a LotusScript agent from anywhere on the form. Just bear in mind if your passing a note ID and picking up that document from the agent, you will not get any unsaved changes. The agent is getting the document with the values stored in the NotesDatabase object, not a back-end representation of a front-end NotesUIDocument. This means if you're wanting to take into account changes the user has made when running your agent, it's really a PostSave event.
If your agent does detailed validation in lotusscript and you want this to trigger pre-save, then you have to re-write it in LotusScript or get creative. Off the top of my head, it might be possible to create a temporary document in server-side javascript with the values you need, save that, submit that in a hidden panel and return any success or failure message. That's a bit crude, but I'm sure the principle could be refined into something more sophisticated and possible a reusable custom control of its own.
Regards
Paul
Feedback response number WEBB7UNBRB created by ~Maria Xanjumiberg on 08/06/2009